Version 2021 R1.1

Web Client Build Number: 10.1.1.39191

DataSync Build Number: 10.1.1.38303

August 20, 2021

Breaking Change

  • As of our next full release (2021 R2), Nectari, DataSync and Web Central Point Configurator will no longer support Internet Explorer 11. For an optimal user experience, we strongly recommend using our products in conjunction with a supported browser such as Google Chrome or Microsoft Edge.

Highlights

Note  

As of version 2021 R1.1, when embedding Nectari into your ERP website using a Chromium-based browser, please ensure that your Web Client is bound through HTTPS rather than HTTP. For more information on how to embed your Web Client into your ERP, see Embedding Nectari.

Improvements

Web Client

  • In the Total Row tab of the Worksheet Properties menu, the Total Row Alignment field was added, and Label Text was replaced by Total Row Description (for more info., see Worksheets).

  • In the Column Header tab of the Worksheet Properties menu, a Group Description toggle was added (for more info., see Worksheets).

OLAP Manager

  • In the OLAP Manager, query scripts were improved to be able to use field and table names regardless of the case and Oracle reserved words used.

  • When creating a new Measure in the OLAP Manager, the Summarizable property is now enabled by default.

DataSync

  • Users can now enable the option to receive email notifications to alert them if any scheduled job fails. This option can be enabled from the Users pane of the Settings tab in DataSync (for more info., see Add a User).

  • For Synchronization and Consolidation-type extractions, two new fields—Primary Keys does not contain NULL and Unique Clustered Index—were added to the Extraction window (for more info., see Set Up the Extraction Panel).

  • For Flat File-type connectors, additional connection properties were added, and double fields from the source will now appear as decimals in the destination (for more info., see Settings for Flat File).

  • A job re-attempt policy was implemented for unsuccessful jobs. Jobs that cannot be completed will now be re-executed 3 times before failing if the third re-attempt is unsuccessful.

  • DataSync extraction logs will now be saved for a maximum number of days (7 days by default) rather than a maximum number of log entries.

  • For Sage Intacct connections, additional connection properties were added.

  • For Sage Intacct connections, the process for obtaining field names and object metadata has been improved.

 

Web Client Templates

Universal Data Model

  • A flag field was added to Account Groupings that were imported from an ERP to facilitate Import Procedure syncing.

  • In the Report Account Mapping data model, the prompt on the Generate Account Groupings info page will now show all COAs instead of just the ones in the setup table.

  • In the Finance Module and DimTime cube, logic was added allowing users to select their Fiscal Year as a Start Date or End Date value.

  • The Delete Ledger Type info page now deletes all previously generated rates in addition to the ledger type.

  • Forecasts can now be generated for Margins.

  • A new Forecast generation method has been added that calculates constant growth based on the user's Last Year values.

Sage 200 UK

  • In the DimTime cube, the UDM_S200UKFCALENDAR table is now a view.

  • In the Finance Staging cube, the BudgetValue filter was added to the Budget and Yearly Budget data sources to improve loading times.

Sage Intacct

  • For the Transaction data source, in the Finance Staging cube, the Document Number value is now mapped from the Document field to the Batchno on Glbatch.

DataSync

  • Extraction issues caused by the CCTRANSACTIONENTRY and GLBUDGETHEADER tables were fixed.

Sage X3

  • After generating a forecast, Stored Procedures can now be loaded back into Sage X3.

Sage 100 Template

  • Prompts, Global Variables and reviewed Headers were added to the GL Financial data model.

  • Prompts, Global Variables and reviewed Headers were added to the Invoice History data model.

DataSync

  • In Sage 100 Standard consolidation extractions, the Primary Key and Tracking Key definitions for the GL_Options table were updated.

Sage 300 Template

  • Optional Field logic has been changed to Optional Field ETL.

Sage Intacct Template

DataSync

  • The Vendor table was moved from the NoRefresh extraction to the Refresh extraction.

  • The GLAcctGrpMember table was added to the Refresh extraction.

Sage X3 Template

  • The Budget Info Page now supports additional CCE and DIE dimensions for Sage X3 v10 and above.

  • In Data Model Expenses, Dimension Type descriptions are now attached in Analytical Dimensions 4 through 9.

  • In ETNA, the deprecated fields from Sage X3 2021R3 have been desynchronised.

Sage XRT Template

  • Users will now be able to view data in the Currency Rate view even if they only have one currency and no rates.

Central Point Library Template

  • A new Data Model was added that shows OLAP job status and information.

 

Fixes

Web Client

  • When performing a drill down after a drill up in a Combination Chart type View, the data was sometimes not refreshed to reflect the current filter.

  • The Simple Gauge view as well as all Map views (except for the Google Map view) were not displayed correctly when exported.

  • Views were unable to be exported to .xls or .xlsx format if they contained more than 6 expanded groups (for more info., see Exporting Documents).

  • After performing drill down actions in a Vertical Bar Chart, the data was sometimes not automatically refreshed.

  • In Gauge views, users were unable to save label and location Gauge Property configurations.

  • Saved layout configurations were not retained on Views that contained filters when the View was closed and re-opened.

  • In Worksheets, an error could occur when attempting to add a filter via the UI or when expanding a group within a Boolean-type field.

  • Subtotal Exceptions were appearing as blank on the grid if both Groups and Pivots were applied.

  • In the Selection Page and Advanced Filter windows, various errors associated with the Date field occurred when using an SQL Server user language other than English. These error messages also sometimes appeared when attempting to expand a Date field on the Grid.

  • For SQL queries that were validated in the Advanced Filter window, an unexpected GROUP BY clause was being added, which extended the duration of the validation.

  • For Window Functions configured in the Data Model Designer, the ORDER BY parameter was only applying to the last field.

  • There were multiple visual issues present on Dashboards that used dark or silver Themes.

  • In exports to .xls or .xlsx format, users received an error message when attempting to open the export in Excel if the file contained a header or footer made up of more than 255 combined characters.

  • In exports, there were occasionally currency formatting issues present in the User Calculated and Report Calculated columns.

  • In the Data Model Designer SQL Scripts Builder, selecting the DATENAME or DATEPART function input the Day function rather than the desired one.

  • In connections with Oracle-type Central Points, images were not loaded in Report titles.

  • In connections with Oracle-type Central Points, the Import Template feature was unable to import Dashboards that contained a Dockable Filter Control.

  • In the Global Variables menu, using the search bar made it possible to create duplicate variables which caused errors when attempting to log in.

  • In the Global Variables menu, when creating a new variable after using the search function, the Data Source field disappeared if the JavaScript variable type was selected.

Distribution

  • In distributed reports that contained dynamic global variables, the variables were not showing the correct values unless the user manually saved the report before each distribution.

  • In jobs created through the Scheduler, there was a column formatting issue in distributions that contained a global variable.

OLAP Manager

  • In the OLAP Manager Scheduler, jobs that were set to recur monthly would not save if too many days or months were selected.

  • Index creation requests for history tables would sometimes time out, which was inconsistent with the other OLAP manager functionalities.

  • In the Logs section of the OLAP Manager, entries in the Group ID column were lacking a.m. or p.m. in their timestamp.

  • For jobs configured in the OLAP Manager Scheduler, the selected recurrence interval was not always respected.

Note  

Users that already had jobs configured in the OLAP Manager Scheduler prior to this version will need to save their configurations again in order for this fix to take effect.

Excel Add-In

  • If a Reporting Tree contained a node with multiple values, users would receive an error message when attempting to use that node in the Excel Add-in.

  • In email or network share distributions, setting the cell value sometimes caused output file names to exceed 255 characters which led to an error message when attempting to open the file.

  • In Excel Add-in, the default value for stored procedures was not automatically populated.

DataSync

  • Memory leaks associated with scheduled jobs and the Run Extraction Now feature were detected on several connection types.

  • Web API memory management was improved to avoid OutOfMemoryException errors.

  • When exporting extractions with multiple tables to CSV format, an error could occur during the Validate and Build phase if one of the tables had previously failed.

  • The error message that appeared when users attempted to activate a licence that had already reached its maximum number of activations was not very clear.

  • Extractions incorrectly remained in Running status throughout source connection issues or IIS server crashes.

  • When cancelling an ongoing job, the extraction status was not updated until the source query was finished executing.

  • For jobs configured in the DataSync Scheduler, the selected recurrence interval was not always respected.

Note  

Users that already had jobs configured in the DataSync Scheduler prior to this version will need to save their configurations again in order for this fix to take effect.

Web Client Templates

Universal Data Model

  • When creating a new Ledger Type, rates were sometimes not generated if rates had already been generated for a second Ledger Type.

  • When creating a new Ledger Type in the Finance cube, there were occasionally issues with the Tracking feature for the 2- Posting and 2- Summarized data sources.

  • When creating a new Ledger Type, the Opening Balance was not always recalculated correctly when moving the Fiscal Period backwards.

  • When creating a new Ledger Type in the Finance cube, a missing Join for 2- OLAP Posting New Ledger on LEDTYP sometimes caused duplicate amounts.

  • When generating a Forecast on some ERPs, the Invoice Date was being used for returns rather than the Return Date.

  • For the UDM_FILL_REPORT_MAP_GROUP stored procedure in the Account Grouping Setup data model, subgroup logic did not work properly if the user had more than 2 subgroups.

  • The default value of the UDM_FISCALYEAR_END_BGN global variable was incorrectly set to 1. Its default value is now 0 (zero).

Sage 200 UK Template

  • In the Nominal Ledger data model, Balance and Report Balance calculations have been updated.

  • For worksheets in the Nominal Ledger data model, the Reverse Data feature sometimes produced numbers that were not the correct sign (i.e., positive or negative). To rectify this issue, the Posting and Balance fields were replaced by the Report Posting and Report Balance fields and the Reverse Data feature was disabled.

  • The NEC_REORGANIZE_FIN_REPORTS script now sometimes uses NLFinancialReportRow instead of NEC_NLFinancialReportRow.

Sage 300 Template

  • In the Data Model Account Summary, the GLAMF-to-GLACGRP Join was changed from ACCTGRPSCD to ACCTGRPCOD.

DataSync

  • Calculations using the LASTMODIFIED tracking key sometimes returned incorrect data.

Sage X3 Template

  • The Report Income Statement feature did not work due to the Delete Reporting Tree function failing to remove the attached Reporting Tree from the report after being deleted.